@copilot Should endpoint keys in user-facing schemas include a leading slash ('users/{id}' vs '/users/{id}'), or should I normalize both?

• normalize both

Can I assume request/response definitions may be plain runtype-object literals (e.g., { id: String }) and I should auto-wrap them (with Record) for runtime guards?

• Yes, correct

Is body optional for GET by definition (i.e., disallow bodies for GET/DELETE), or should I just rely on the helpers’ defaults?

• when http verbs not allow Body, the property should be excluded.

@copilot Should endpoint keys in user-facing schemas include a leading slash ('users/{id}' vs '/users/{id}'), or should I normalize both?

• normalize both
  ...

Implemented: paths now normalize with or without leading slash, request/response objects are auto-wrapped into runtypes, and body is omitted for verbs that don’t allow it. (49d30ea)

@copilot your changes add a lot of issues! The #file:schema.ts as many errors

@copilot your changes add a lot of issues! The #file:schema.ts as many errors

Schema type errors fixed: relaxed runtype detection, adjusted auto-wrapping, and type-checked cleanly (76221e5).

@copilot The path inference is not working. The follow example in #file:schema.test.ts

1. The id is not extracted from the path 'users/{id}' and is not suggested.
2. The path value is not typed! The follow value is valid path: { www: Number } but www is not a valid parameter name!
3. The path property should be excluded when the path string not contains a valid params.

 const schema = {
      'users/{id}': GET({
        path: { id: Number },
        responses: {
          200: { name: String },
          404: { error: String },
        },
      }),
    };

@copilot The path inference is not working. The follow example in #file:schema.test.ts

1. The id is not extracted from the path 'users/{id}' and is not suggested....

Path params are now inferred and validated: keys are derived from the route template, invalid names like path: { www: Number } are rejected, and path is disallowed when the route has no params. (66c1fce)